feat(bolt-vite-react-ts): modernize toolchain and remove eslint - #120
Open
d3lm wants to merge 1 commit into
Open
feat(bolt-vite-react-ts): modernize toolchain and remove eslint#120d3lm wants to merge 1 commit into
d3lm wants to merge 1 commit into
Conversation
|
|
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Rebuild the template on the current create-vite baseline which is Vite 8, React 19, Tailwind 4 and TypeScript 6. Tailwind v4 is configured in CSS, so
tailwind.config.js,postcss.config.jsand thepostcssandautoprefixerdeps are gone and.bolt/promptnow explains the@thememodel so generated apps do not recreate a JS config.I also dropped ESLint entirely, which cuts the install from 181 to 59 packages and meaningfully speeds up npm install in WebContainer.
TypeScript 7 theoretically works but I decided to stay on 6 for now.
I also fixed
removeFileHashin the test utils. Vite content hashes are base64url and may contain-, which the previous regex mis-stripped.Intention behind this is that our base starter template has a clean
auditreport with 0 vulnerabilities.Closes BOAI-983